APPLICATION RESILIENCY USING APIs

ABSTRACT

An approach is provided for managing resiliency of an application. Based on information specifying services provided by service providers (SPs) which is stored in a configuration management database, a topology mapping a first service provided by a first SP to a second service provided by a second SP is generated. Each of the first and second services provides a functionality of the application. A fail condition of the first SP is detected. Based on the topology, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API provided by the first SP is disabled and the second API is activated, thereby continuing to provide the functionality of the application even though the first SP is experiencing the fail condition.

BACKGROUND

The present invention relates to managing applications, and moreparticularly to managing resiliency of an application that initiallyuses services provided by a service provider, where resiliency isimproved by redeploying the services to a second service provider inresponse to the first service provider experiencing an outage.

In many cases, an organization builds an information technology solutionusing the services provided by various service providers (SPs). Thesolution may be a cloud-based solution provided by various cloud serviceproviders (CSPs). For example, one component of the solution resides ona cloud provided by CSP 1 while another component resides on anothercloud provided by CSP 2. Because of the prohibitive cost, theorganization does not have a hot or cold disaster recovery site, whichleads to a significant amount of time needed to restore service for thesolution.

SUMMARY

In a first embodiment, the present invention provides a method ofmanaging resiliency of an application provided by a first serviceprovider (SP). The method includes a computer receiving informationspecifying services which are provided by respective SPs including thefirst SP. The received information indicates that each of the servicesprovides a functionality of the application. The method further includesthe computer storing the received information in a configurationmanagement database (CMDB). The method further includes based on theinformation stored in the CMDB, the computer generating a topology whichmaps the first SP to a second SP included in the SPs and maps a firstservice provided by the first SP to a second service provided by thesecond SP. The first and second services are included in the servicesspecified by the received information. The method further includessubsequent to the step of generating the topology, the computerdetecting a fail condition of the first SP, which indicates an outage ofthe first service provided by the first SP. The method further includesin response to the step of detecting the fail condition and based on thetopology, the computer determining that a first API provided by thefirst SP had provided the first service prior to the fail condition andthat a second API provided by the second SP provides the second service.The method further includes based on the first API having provided thefirst service and the second API providing the second service, thecomputer disabling the first API provided by the first SP and activatingthe second API provided by the second SP, so that the functionality ofthe application that had been provided by the first service prior to thefail condition being detected continues by being provided by the secondAPI even though the first SP is experiencing the fail condition.

In a second embodiment, the present invention provides a computerprogram product including a computer-readable storage device and acomputer-readable program code stored in the computer-readable storagedevice. The computer-readable program code includes instructions thatare executed by a central processing unit (CPU) of a computer system toimplement a method of managing resiliency of an application provided bya first service provider (SP). The method includes a computer systemreceiving information specifying services which are provided byrespective SPs including the first SP. The received informationindicates that each of the services provides a functionality of theapplication. The method further includes the computer system storing thereceived information in a configuration management database (CMIDB). Themethod further includes based on the information stored in the CMIDB,the computer system generating a topology which maps the first SP to asecond SP included in the SPs and maps a first service provided by thefirst SP to a second service provided by the second SP. The first andsecond services are included in the services specified by the receivedinformation. The method further includes subsequent to the step ofgenerating the topology, the computer system detecting a fail conditionof the first SP, which indicates an outage of the first service providedby the first SP. The method further includes in response to the step ofdetecting the fail condition and based on the topology, the computersystem determining that a first API provided by the first SP hadprovided the first service prior to the fail condition and that a secondAPI provided by the second SP provides the second service. The methodfurther includes based on the first API having provided the firstservice and the second API providing the second service, the computersystem disabling the first API provided by the first SP and activatingthe second API provided by the second SP, so that the functionality ofthe application that had been provided by the first service prior to thefail condition being detected continues by being provided by the secondAPI even though the first SP is experiencing the fail condition.

In a third embodiment, the present invention provides a computer systemincluding a central processing unit (CPU); a memory coupled to the CPU;and a computer-readable storage device coupled to the CPU. The storagedevice includes instructions that are executed by the CPU via the memoryto implement a method of managing resiliency of an application providedby a first service provider (SP). The method includes a computer systemreceiving information specifying services which are provided byrespective SPs including the first SP. The received informationindicates that each of the services provides a functionality of theapplication. The method further includes the computer system storing thereceived information in a configuration management database (CMDB). Themethod further includes based on the information stored in the CMDB, thecomputer system generating a topology which maps the first SP to asecond SP included in the SPs and maps a first service provided by thefirst SP to a second service provided by the second SP. The first andsecond services are included in the services specified by the receivedinformation. The method further includes subsequent to the step ofgenerating the topology, the computer system detecting a fail conditionof the first SP, which indicates an outage of the first service providedby the first SP. The method further includes in response to the step ofdetecting the fail condition and based on the topology, the computersystem determining that a first API provided by the first SP hadprovided the first service prior to the fail condition and that a secondAPI provided by the second SP provides the second service. The methodfurther includes based on the first API having provided the firstservice and the second API providing the second service, the computersystem disabling the first API provided by the first SP and activatingthe second API provided by the second SP, so that the functionality ofthe application that had been provided by the first service prior to thefail condition being detected continues by being provided by the secondAPI even though the first SP is experiencing the fail condition.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for providing resiliency to anapplication, in accordance with embodiments of the present invention.

FIGS. 2A-2B depict a flowchart of a process of providing resiliency toan application, where the process is implemented in the system of FIG.1, in accordance with embodiments of the present invention.

FIG. 3 depicts a table of exemplary rules in a configuration managementdatabase included in the system of FIG. 1, in accordance withembodiments of the present invention.

FIG. 4 is an example of a re-instantiation of an application to provideresiliency in the process of FIGS. 2A-2B, in accordance with embodimentsof the present invention.

FIG. 5 is a concept model of a recovery of an exemplary applicationprovided in the process of FIGS. 2A-2B, in accordance with embodimentsof the present invention.

FIG. 6 is a sequence diagram of an exemplary recovery of an applicationprovided in the process of FIGS. 2A-2B, in accordance with embodimentsof the present invention.

FIG. 7 is a block diagram of a computer that is included in the systemof FIG. 1 and that implements the process of FIGS. 2A-2B, in accordancewith embodiments of the present invention.

FIG. 8 depicts a cloud computing environment, in accordance withembodiments of the present invention.

FIG. 9 depicts abstraction model layers, in accordance with embodimentsof the present invention.

DETAILED DESCRIPTION Overview

Embodiments of the present invention provide resiliency for anapplication by storing in a configuration management database (CMDB) (i)an inventory of SPs that provide similar services for the applicationand (ii) relevant data specifying the services. In response to a servicedisruption at a first SP that had been servicing the application,embodiments of the present invention provide the aforementionedresiliency by determining a set of APIs that switch the application fromthe first SP to a second SP, where the APIs are determined based oninformation stored in the CMDB. The switch to the second SP ensures thefunctionality of the application is provided even though the first SP isexperiencing the service disruption. In one embodiment, theaforementioned SPs are cloud service providers (CSPs).

The use of the CMDB to determine the set of the APIs that allow adynamic movement of an application from one SP to another SP (1) provideresiliency for small to medium sized businesses that use a computingenvironment in which access to standardized resources owned and managedby a SP is permitted to subscribers on a pay-per-use basis (e.g., apublic cloud), (2) manage and customize the computing environment (e.g.,cloud environment) to meet the needs of individual businesses, (3)enable a business application to efficiently move from one SP to anotherSP (e.g., from one CSP to another CSP), and (4) facilitate businesscontinuity within a computing environment (e.g., cloud environment) orenable optimal recovery from a service outage.

System for Providing Application Resiliency

FIG. 1 is a block diagram of a system 100 for providing resiliency to anapplication, in accordance with embodiments of the present invention. Inone embodiment, system 100 provides resiliency to a cloud-basedapplication. System 100 includes a computer 102 which includes asoftware-based resiliency management system 104, a configurationmanagement database (CMDB) 106, and software-based system scanning tools108. Resiliency management system 104 includes the following software,which is executed by computer 102: application programming interface(API) builder 110, application systems relation builder 112, API faultdetection module 114, and API topology builder 116. System 100 alsoincludes N data centers in communication with computer 102 via a network(not shown). The N data centers are data center 118-1, . . . , datacenter 118-N (i.e., data center 1, . . . , data center N), where N is aninteger greater than one. The N data centers are managed by respectiveSPs. Each of the data centers in system 100 includes a respective set ofapplications and respective computing infrastructure. Data center 118-1includes applications 120 and computing infrastructure 122 and datacenter 118-N includes applications 124 and computing infrastructure 126.In one embodiment, data centers 118-1, . . . , 118-N are N cloud datacenters managed by respective CSPs and the computing infrastructureincluded in each of the cloud data centers is cloud computinginfrastructure.

System scanning tools 108 scan data centers 118-1, . . . , 118-N todetect and receive newly created or updated APIs which provide accessmechanisms to allow an application to be deployed on one of the datacenters 118-1, . . . , 118-N (e.g., an application included inapplications 120 being deployed on data center 118-1). System scanningtools 108 sends the APIs to as input to API builder 110. API builder 110sends the APIs to application systems relation builder 112, whichgenerates a relation or mapping between APIs provided by different SPs.A relation or mapping between API 1 provided by SP 1 and API 2 providedby SP 2 indicates that the functionality provided by API 1 is similar oridentical to a functionality provided by API 2.

API builder 110 also sends the APIs to API fault detection module 114,which checks whether there is a match between APIs that are in arelation that was built by application systems relation builder 112. APIfault detection module 114 also detects whether there is a conflict inusing an API to provide a functionality of an application that isswitching from a one SP to another SP (e.g., an application included inapplications 120 switching from being provided by data center 118-1 tobeing provided by data center 118-N). API fault detection module 114 mayresolve the conflict by receiving a change to the application so thatthe API can be used by the application being switched form one SP toanother SP.

API builder 110 sends the APIs to API topology builder 116, whichgenerates a topology that includes the relations or mappings built byapplication systems relation builder 112. API topology builder 116 usesthe generated topology to create a recovery model that indicates how theapplication (e.g., an application included in applications 120) that hadbeen deployed on a first SP (e.g., data center 118-1) will be redeployedon a second SP (e.g., data center 118-N) in response to a service outageexperienced by the first SP.

In one embodiment, the recovery model includes geographic affinitiesassociated with the APIs that are providing the same or similarapplication functionality. The geographic affinities in the model favora selection of one API over another because the geographic location ofthe SP that provides the selected API provides an acceptable level ofapplication latency based on a predetermined threshold, whereas thegeographic location of the other SP whose API is not selected does notprovide an acceptable application latency.

In one embodiment, the recovery model generated by API topology builder116 includes application-specific re-provisioning requirements, such asa requirement for a threshold amount of bandwidth connectivity betweenthe selected SP and a provider of the application that manages the datafor the application.

In one embodiment, the aforementioned recovery model includesdependencies between the data used for the application and the API.

The functionality of the components shown in FIG. 1 is described in moredetail in the discussion of FIGS. 2A-2B, FIG. 3, FIG. 4, FIG. 5, FIG. 6,and FIG. 7 presented below.

Process for Providing Application Resiliency

FIGS. 2A-2B depict a flowchart of a process of providing resiliency toan application, where the process is implemented in the system of FIG.1, in accordance with embodiments of the present invention. In oneembodiment, the process of FIGS. 2A-2B provides resiliency to acloud-based application. The process of FIGS. 2A-2B starts at step 200in FIG. 2A. In step 202, system scanning tools 108 and API builder 110(see FIG. 1) collect infrastructure information by performinginfrastructure discovery on a current information technology (IT)environment. The information collected in step 202 includes informationspecifying computing infrastructure 122 (see FIG. 1), computinginfrastructure 126 (see FIG. 1), and other computing infrastructurecomponents included in data centers 118-1, . . . , 118-N (see FIG. 1).The information about a computing infrastructure includes a machineserial number, an identification of the operating system, where theinfrastructure is hosted, and a description of the kind of ITenvironment.

In another embodiment, resiliency management system 104 (see FIG. 1)receives the information about computing infrastructure from one or morespreadsheets which are updated by an administrator.

In step 204, resiliency management system 104 (see FIG. 1) determineswhether the infrastructure information collected in step 202 is correct.If any of the infrastructure information collected in step 202 isdetermined to incorrect in step 204, then the No branch of step 204 isfollowed and the process loops back to step 202 in which system scanningtools 108 (see FIG. 1) re-scans the IT environment to collectinfrastructure information that corrects the incorrect infrastructureinformation. Alternatively, the loop back to step 202 includesrequesting the administrator to confirm whether the infrastructureinformation is correct.

If the infrastructure information collected in step 202 is determined tobe correct in step 204, then the Yes branch of step 204 is followed andstep 206 is performed.

In step 206, resiliency management system 104 (see FIG. 1) determineswhether the infrastructure information collected in step 202 matches arecord in CMDB 106 (see FIG. 1). If the infrastructure information doesnot match any record in CMDB 106 (see FIG. 1) (i.e., a new API isdetected in the infrastructure information), then the No branch of step206 is followed and step 208 is performed.

In step 208, resiliency management system 104 builds a data record thatstores the infrastructure information that did not match any record inCMDB 106 (see FIG. 1) in step 206 and stores the newly built data recordin CMDB 106.

Returning to step 206, if the infrastructure information matches arecord in CMDB 106 (see FIG. 1), then the Yes branch of step 206 isfollowed and the process skips step 208 and performs step 210. Step 210also follows step 208.

In step 210, API builder 110 (see FIG. 1) collects data for building anapplication infrastructure mapping. In one embodiment, the collecteddata includes an application identifier (ID), a description of thefunction of the application, the operating system level, and aspecification of the Internet Protocol being used. The data iscollected, for example, via a spreadsheet file.

In step 212, resiliency management system 104 (see FIG. 1) determineswhether the data collected in step 210 is correct. If any of the datacollected in step 210 is determined to be not correct in step 212, thenthe No branch of step 212 is followed and the process loops back to step210 to collect updated data which is correct.

If the data collected in step 210 is determined to be correct in step212, then the Yes branch of step 212 is followed and step 214 isperformed.

In step 214, application systems relation builder 112 (see FIG. 1)builds an application infrastructure mapping which maps an API providedby a first SP to one or more APIs provided by respective one or moreother SPs based on each of the one or more APIs providing identical orsimilar functionality as the functionality of the API provided by thefirst SP. For a particular infrastructure, building an applicationinfrastructure mapping in step 214 includes (1) a top down approach fromthe infrastructure level (i.e., from the business application level,application systems relation builder 112 (see FIG. 1) maps all theinformation that is associated with the particular infrastructure) and(2) a bottom up approach from all the applications to theinfrastructure. In one embodiment, application systems relation builder112 (see FIG. 1) in step 214 builds an application infrastructuremapping which maps an API provided by a first CSP to one or more APIsprovided by respective one or more other CSPs based on each of the oneor more APIs providing identical or similar functionality as thefunctionality of the API provided by the first CSP.

In step 216, resiliency management system 104 (see FIG. 1) determineswhether the application infrastructure mapping built in step 214 iscomplete and correct by checking data in CMDB 106 (see FIG. 1). If theapplication infrastructure mapping is determined in step 216 to be notcomplete, not correct, or both not complete and not correct, then the Nobranch of step 216 is followed and the process loops back to step 214 inwhich application systems relation builder 112 re-builds the applicationinfrastructure mapping to make the mapping complete if the mapping hadbeen incomplete and correct if the mapping had been incorrect. Forexample, the validation of the mapping in step 216 includes checkingwhether a lack of an identification of nodes connected to a server iscorrect. The lack of nodes may be correct because the server is astandalone server, or the lack of nodes may be incorrect because theserver is a client server and all servers connected to the client serverneed to be identified in the mapping.

If the application infrastructure mapping is determined to be completeand correct in step 216, then the Yes branch of step 216 is followed andthe process continues in step 218 in FIG. 2B.

In step 218, API fault detection module 114 (see FIG. 1) determineswhether any faults are detected in the APIs in the applicationinfrastructure mapping built in step 214 (see FIG. 2A). If any fault isdetected in step 218, then the Yes branch of step 218 is followed andstep 220 is performed.

In step 220, application systems relation builder 112 (see FIG. 1)rebuilds the application infrastructure mapping.

Returning to step 218, if no fault in the application infrastructuremapping is detected, then the No branch of step 218 is followed, step220 is skipped and step 222 is performed. Step 222 also follows step220, which was described above.

In step 222, API topology builder 116 (see FIG. 1) builds a topologybased on the application infrastructure mapping. The topology is a basisfor a recovery model by which an application is switched from beingprovided by a first SP to being provided by a second SP in response to adetermination that the first SP is experiencing an outage or serviceinterruption. In one embodiment, the topology is a basis for a recovermodel by which an application is switched from being provided by a firstCSP to being provided by a second CSP in response to a determinationthat the first CSP is experiencing an outage or service interruption.

In step 224, resiliency management system 104 (see FIG. 1) determineswhether the topology built in step 222 is complete. If the topologybuilt in step 222 is determined to be incomplete in step 224, then theNo branch is followed and the process loops back to step 222 in whichAPI topology builder re-checks data in CMDB 106 (see FIG. 1) and themapping built in step 214 (see FIG. 2A) and re-builds the topology togenerate a complete topology.

If the topology built in step 222 is determined in step 224 to becomplete, then the Yes branch of step 224 is followed and step 226 isperformed.

In step 226, API topology builder 116 (see FIG. 1) builds a recoverymodel (i.e., a resiliency facility) based on the topology built in step222. API topology builder 116 (see FIG. 1) creates an API which is usedfor the recovery model associated with a particular SP. The recoverymodel specifies the particular layer of the computing environment (e.g.,service layer), an identification of the SP, deployment details,operating system details, configuration network details, and the type ofthe application. In one embodiment, the API created by API topologybuilder 116 (see FIG. 1) is used for the recovery model associated witha particular CSP and the recovery model specifies the particular layerof the cloud environment, and an identification of the CSP, along withthe type of application and the details of deployment, the operatingsystem, and configuration network.

In step 228, the process of FIGS. 2A-2B ends.

Configuration Management Database

FIG. 3 depicts a table 300 of exemplary rules stored in a configurationmanagement database included in the system of FIG. 1, in accordance withembodiments of the present invention. Table 300 includes accessmechanisms 302, which include deploy a virtual machine (VM), configurethe VM, deploy a network, configure the network, deploy middleware,configure middleware, deploy an application, and configure theapplication. Access mechanisms 302 specify deployment and configurationof services provided by portals of CSP 1, CSP 2, and CSP 3. During step222 (see FIG. 2B), resiliency management system 104 (see FIG. 1)generates and stores rules 304, 306, and 308 for access mechanism“Deploy VM” for Cloud Service Provider 1, Cloud Service Provider 2, andCloud Service Provider 3, respectively. For example, rules 304, 306, and308 are rules stored in CMDB 106 (see FIG. 1) which specify respectiveAPIs for deploying a VM, where the APIs are provided by respectiveportals of Cloud Service Provider 1, Cloud Service Provider 2, and CloudService Provider 3.

FIG. 4 is an example of a re-instantiation of an application to provideresiliency in the process of FIGS. 2A-2B, in accordance with embodimentsof the present invention. A first cloud 402 and a second cloud 404access CMDB 406, which is an example of CMDB 106 in FIG. 1. A customer(e.g., an application developer) using clouds 402 and 404 developsapplications that can use and maintain either data 408 in a database ina first location or data 410 in another database in a second location,where data 410 is a backup of data 408. Subsequent to the applicationsrunning on cloud 402, resiliency management system 104 (see FIG. 1)detects a fail condition in cloud 402 indicating a complete cloud datacenter outage. In response to the detection of the fail condition,resiliency management system 104 (see FIG. 1) uses APIs included in CMDB406 to re-instantiate the applications that had been running on cloud402 onto cloud 404. After re-instantiating the applications, theapplications running on cloud 404 use data 410.

FIG. 5 is a concept model 500 of a recovery of an exemplary applicationprovided in the process of FIGS. 2A-2B, in accordance with embodimentsof the present invention. Concept model 500 includes locations 502, 504,506, and 508. Location 502 is Cloud A and location 504 is Cloud B. Eachcloud has a provisioning portal. Cloud A includes a node 510, whichindicates a deployment portal. Similarly, Cloud B includes a node 512,which indicates a deployment portal.

Location 506 is a Recovery Farm that provides the functionality ofresiliency management system 104 (see FIG. 1). The Recovery Farmincludes a recovery application node 514 and a recovery CMDB node 516.Location 508 is a Customer location which includes a customer portalnode 518 and a customer data node 520. Recover application node 514includes a recovery application that manages the recovery process interms of communication with deployment portal nodes 510 and 512. Usinginformation from the CMDB included in recovery CMDB node 516, theRecovery Farm transfers services from Cloud A to Cloud B.

Recovery of an Application

FIG. 6 is a sequence diagram 600 of an exemplary recovery of anapplication provided in the process of FIGS. 2A-2B, in accordance withembodiments of the present invention. Sequence diagram 600 includes acloud 602 (i.e., Cloud A), a customer 604, a recovery farm 606, and acloud 608 (i.e., Cloud B). Recovery farm 606 includes the functionalityof resiliency management system 104 (see FIG. 1). Customer 604 (i.e., acustomer's computer system) hosts the main portal and data for thecustomer's service, while Cloud A and Cloud B are service providers thatrender the applications that service the customer data. In step 1, acustomer portal of customer 604 is notified of a fail condition in CloudA by which a recovery of the applications to a backup cloud serviceprovider is needed. In step 2, customer 604 notifies a recovery serviceof recovery farm 606 about the fail condition and the need for recoveryof the applications to a backup cloud. Recovery farm 606 uses CMDB 106(see FIG. 1) to identify Cloud B as the backup cloud service providerfor the applications. In step 2.1 and in response to identifying CloudB, recovery farm 606 disables the APIs to Cloud A.

In step 3, recovery farm 606 activates the APIs to Cloud B via CMDB 106(see FIG. 1) and sends a provisioning message to Cloud B. In step 3.1and in response to receiving the provisioning message, Cloud B sends amessage to recovery farm 606 indicating that activation of the APIs toCloud B is complete. In step 4, recovery farm 606 notifies the customerportal of customer 604 of the success of the recovery of theapplications on Cloud B.

Computer System

FIG. 7 is a block diagram of a computer 102 that is included in thesystem of FIG. 1 and that implements the process of FIGS. 2A-2B, inaccordance with embodiments of the present invention. Computer 102 is acomputer system that generally includes a central processing unit (CPU)702, a memory 704, an input/output (I/O) interface 706, and a bus 708.Further, computer 102 is coupled to I/O devices 710 and a computer datastorage unit 712. CPU 702 performs computation and control functions ofcomputer 102, including executing instructions included in program code714 for resiliency management system 104 (see FIG. 1) to perform amethod of managing resiliency of an application, where the instructionsare executed by CPU 702 via memory 704. In the discussion of FIG. 7, theapplication whose resiliency is managed may be a cloud-basedapplication. CPU 702 may include a single processing unit, or bedistributed across one or more processing units in one or more locations(e.g., on a client and server).

Memory 704 includes a known computer readable storage medium, which isdescribed below. In one embodiment, cache memory elements of memory 704provide temporary storage of at least some program code (e.g., programcode 714) in order to reduce the number of times code must be retrievedfrom bulk storage while instructions of the program code are executed.Moreover, similar to CPU 702, memory 704 may reside at a single physicallocation, including one or more types of data storage, or be distributedacross a plurality of physical systems in various forms. Further, memory704 can include data distributed across, for example, a local areanetwork (LAN) or a wide area network (WAN).

I/O interface 706 includes any system for exchanging information to orfrom an external source. I/O devices 710 include any known type ofexternal device, including a display device, keyboard, etc. Bus 708provides a communication link between each of the components in computer102, and may include any type of transmission link, includingelectrical, optical, wireless, etc.

I/O interface 706 also allows computer 102 to store information (e.g.,data or program instructions such as program code 714) on and retrievethe information from computer data storage unit 712 or another computerdata storage unit (not shown). Computer data storage unit 712 includes aknown computer-readable storage medium, which is described below. In oneembodiment, computer data storage unit 712 is a non-volatile datastorage device, such as a magnetic disk drive (i.e., hard disk drive) oran optical disc drive (e.g., a CD-ROM drive which receives a CD-ROMdisk).

Memory 704 and/or storage unit 712 may store computer program code 714that includes instructions that are executed by CPU 702 via memory 704to manage resiliency of an application. Although FIG. 7 depicts memory704 as including program code, the present invention contemplatesembodiments in which memory 704 does not include all of code 714simultaneously, but instead at one time includes only a portion of code714.

Further, memory 704 may include an operating system (not shown) and mayinclude other systems not shown in FIG. 7.

Storage unit 712 and/or one or more other computer data storage units(not shown) that are coupled to computer 102 may store CMDB 106 (seeFIG. 1).

As will be appreciated by one skilled in the art, in a first embodiment,the present invention may be a method; in a second embodiment, thepresent invention may be a system; and in a third embodiment, thepresent invention may be a computer program product.

Any of the components of an embodiment of the present invention can bedeployed, managed, serviced, etc. by a service provider that offers todeploy or integrate computing infrastructure with respect to managingresiliency of an application. Thus, an embodiment of the presentinvention discloses a process for supporting computer infrastructure,where the process includes providing at least one support service for atleast one of integrating, hosting, maintaining and deployingcomputer-readable code (e.g., program code 714) in a computer system(e.g., computer 102) including one or more processors (e.g., CPU 702),wherein the processor(s) carry out instructions contained in the codecausing the computer system to manage resiliency of an application.Another embodiment discloses a process for supporting computerinfrastructure, where the process includes integrating computer-readableprogram code into a computer system including a processor. The step ofintegrating includes storing the program code in a computer-readablestorage device of the computer system through use of the processor. Theprogram code, upon being executed by the processor, implements a methodof managing resiliency of an application.

While it is understood that program code 714 for managing resiliency ofan application may be deployed by manually loading directly in client,server and proxy computers (not shown) via loading a computer-readablestorage medium (e.g., computer data storage unit 712), program code 714may also be automatically or semi-automatically deployed into computer102 by sending program code 714 to a central server or a group ofcentral servers. Program code 714 is then downloaded into clientcomputers (e.g., computer 102) that will execute program code 714.Alternatively, program code 714 is sent directly to the client computervia e-mail. Program code 714 is then either detached to a directory onthe client computer or loaded into a directory on the client computer bya button on the e-mail that executes a program that detaches programcode 714 into a directory. Another alternative is to send program code714 directly to a directory on the client computer hard drive. In a casein which there are proxy servers, the process selects the proxy servercode, determines on which computers to place the proxy servers' code,transmits the proxy server code, and then installs the proxy server codeon the proxy computer. Program code 714 is transmitted to the proxyserver and then it is stored on the proxy server.

Another embodiment of the invention provides a method that performs theprocess steps on a subscription, advertising and/or fee basis. That is,a service provider, such as a Solution Integrator, can offer to create,maintain, support, etc. a process of managing resiliency of anapplication. In this case, the service provider can create, maintain,support, etc. a computer infrastructure that performs the process stepsfor one or more customers. In return, the service provider can receivepayment from the customer(s) under a subscription and/or fee agreement,and/or the service provider can receive payment from the sale ofadvertising content to one or more third parties.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) (memory 704 and computer data storageunit 712) having computer readable program instructions 714 thereon forcausing a processor (e.g., CPU 702) to carry out aspects of the presentinvention.

The computer readable storage medium can be a tangible device that canretain and store instructions (e.g., program code 714) for use by aninstruction execution device (e.g., computer 102). The computer readablestorage medium may be, for example, but is not limited to, an electronicstorage device, a magnetic storage device, an optical storage device, anelectromagnetic storage device, a semiconductor storage device, or anysuitable combination of the foregoing. A non-exhaustive list of morespecific examples of the computer readable storage medium includes thefollowing: a portable computer diskette, a hard disk, a random accessmemory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), a static random access memory(SRAM), a portable compact disc read-only memory (CD-ROM), a digitalversatile disk (DVD), a memory stick, a floppy disk, a mechanicallyencoded device such as punch-cards or raised structures in a groovehaving instructions recorded thereon, and any suitable combination ofthe foregoing. A computer readable storage medium, as used herein, isnot to be construed as being transitory signals per se, such as radiowaves or other freely propagating electromagnetic waves, electromagneticwaves propagating through a waveguide or other transmission media (e.g.,light pulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions (e.g., program code 714)described herein can be downloaded to respective computing/processingdevices (e.g., computer 102) from a computer readable storage medium orto an external computer or external storage device (e.g., computer datastorage unit 712) via a network (not shown), for example, the Internet,a local area network, a wide area network and/or a wireless network. Thenetwork may comprise copper transmission cables, optical transmissionfibers, wireless transmission, routers, firewalls, switches, gatewaycomputers and/or edge servers. A network adapter card (not shown) ornetwork interface (not shown) in each computing/processing devicereceives computer readable program instructions from the network andforwards the computer readable program instructions for storage in acomputer readable storage medium within the respectivecomputing/processing device.

Computer readable program instructions (e.g., program code 714) forcarrying out operations of the present invention may be assemblerinstructions, instruction-set-architecture (ISA) instructions, machineinstructions, machine dependent instructions, microcode, firmwareinstructions, state-setting data, or either source code or object codewritten in any combination of one or more programming languages,including an object oriented programming language such as Smalltalk, C++or the like, and conventional procedural programming languages, such asthe “C” programming language or similar programming languages. Thecomputer readable program instructions may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider). In some embodiments, electronic circuitry including, forexample, programmable logic circuitry, field-programmable gate arrays(FPGA), or programmable logic arrays (PLA) may execute the computerreadable program instructions by utilizing state information of thecomputer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations (e.g., FIGS. 2A-2B and FIG. 6) and/or blockdiagrams (e.g., FIG. 1 and FIG. 7) of methods, apparatus (systems), andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerreadable program instructions (e.g., program code 714).

These computer readable program instructions may be provided to aprocessor (e.g., CPU 702) of a general purpose computer, special purposecomputer, or other programmable data processing apparatus (e.g.,computer 102) to produce a machine, such that the instructions, whichexecute via the processor of the computer or other programmable dataprocessing apparatus, create means for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks. Thesecomputer readable program instructions may also be stored in a computerreadable storage medium (e.g., computer data storage unit 712) that candirect a computer, a programmable data processing apparatus, and/orother devices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions (e.g., program code 714) mayalso be loaded onto a computer (e.g. computer 102), other programmabledata processing apparatus, or other device to cause a series ofoperational steps to be performed on the computer, other programmableapparatus or other device to produce a computer implemented process,such that the instructions which execute on the computer, otherprogrammable apparatus, or other device implement the functions/actsspecified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While embodiments of the present invention have been described hereinfor purposes of illustration, many modifications and changes will becomeapparent to those skilled in the art. Accordingly, the appended claimsare intended to encompass all such modifications and changes as fallwithin the true spirit and scope of this invention.

Cloud Computing Environment

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-Demand Self-Service:

a cloud consumer can unilaterally provision computing capabilities, suchas server time and network storage, as needed automatically withoutrequiring human interaction with the service's provider.

Broad Network Access:

capabilities are available over a network and accessed through standardmechanisms that promote use by heterogeneous thin or thick clientplatforms (e.g., mobile phones, laptops, and PDAs).

Resource Pooling:

the provider's computing resources are pooled to serve multipleconsumers using a multi-tenant model, with different physical andvirtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid Elasticity:

capabilities can be rapidly and elastically provisioned, in some casesautomatically, to quickly scale out and rapidly released to quicklyscale in. To the consumer, the capabilities available for provisioningoften appear to be unlimited and can be purchased in any quantity at anytime.

Measured Service:

cloud systems automatically control and optimize resource use byleveraging a metering capability at some level of abstractionappropriate to the type of service (e.g., storage, processing,bandwidth, and active user accounts). Resource usage can be monitored,controlled, and reported, providing transparency for both the providerand consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS):

the capability provided to the consumer is to use the provider'sapplications running on a cloud infrastructure. The applications areaccessible from various client devices through a thin client interfacesuch as a web browser (e.g., web-based e-mail). The consumer does notmanage or control the underlying cloud infrastructure including network,servers, operating systems, storage, or even individual applicationcapabilities, with the possible exception of limited user-specificapplication configuration settings.

Platform as a Service (PaaS):

the capability provided to the consumer is to deploy onto the cloudinfrastructure consumer-created or acquired applications created usingprogramming languages and tools supported by the provider. The consumerdoes not manage or control the underlying cloud infrastructure includingnetworks, servers, operating systems, or storage, but has control overthe deployed applications and possibly application hosting environmentconfigurations.

Infrastructure as a Service (IaaS):

the capability provided to the consumer is to provision processing,storage, networks, and other fundamental computing resources where theconsumer is able to deploy and run arbitrary software, which can includeoperating systems and applications. The consumer does not manage orcontrol the underlying cloud infrastructure but has control overoperating systems, storage, deployed applications, and possibly limitedcontrol of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private Cloud:

the cloud infrastructure is operated solely for an organization. It maybe managed by the organization or a third party and may existon-premises or off-premises.

Community Cloud:

the cloud infrastructure is shared by several organizations and supportsa specific community that has shared concerns (e.g., mission, securityrequirements, policy, and compliance considerations). It may be managedby the organizations or a third party and may exist on-premises oroff-premises.

Public Cloud:

the cloud infrastructure is made available to the general public or alarge industry group and is owned by an organization selling cloudservices.

Hybrid Cloud:

the cloud infrastructure is a composition of two or more clouds(private, community, or public) that remain unique entities but arebound together by standardized or proprietary technology that enablesdata and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 8, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A, 54B,54C and 54N shown in FIG. 8 are intended to be illustrative only andthat computing nodes 10 and cloud computing environment 50 cancommunicate with any type of computerized device over any type ofnetwork and/or network addressable connection (e.g., using a webbrowser).

Referring now to FIG. 9, a set of functional abstraction layers providedby cloud computing environment 50 (see FIG. 8) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 9 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and optimal event routing to solvers 120-1, .. . , 120-N (see FIG. 1) for event resolution 96.

What is claimed is:
 1. A method of managing resiliency of an applicationprovided by a first service provider (SP), the method comprising thesteps of: a computer receiving information specifying services which areprovided by respective SPs including the first SP, the informationindicating that each of the services provides a functionality of theapplication; the computer storing the received information in aconfiguration management database (CMDB); based on the informationstored in the CMDB, the computer generating a topology which maps thefirst SP to a second SP included in the SPs and maps a first serviceprovided by the first SP to a second service provided by the second SP,the first and second services being included in the services specifiedby the received information; subsequent to the step of generating thetopology, the computer detecting a fail condition of the first SP, whichindicates an outage of the first service provided by the first SP; inresponse to the step of detecting the fail condition and based on thetopology, the computer determining that a first API provided by thefirst SP had provided the first service prior to the fail condition andthat a second API provided by the second SP provides the second service;based on the first API having provided the first service and the secondAPI providing the second service, the computer disabling the first APIprovided by the first SP and activating the second API provided by thesecond SP, so that the functionality of the application that had beenprovided by the first service prior to the fail condition being detectedcontinues by being provided by the second API even though the first SPis experiencing the fail condition.
 2. The method of claim 1, furthercomprising the steps of: the computer receiving other informationspecifying the application and infrastructure components of the SPs,which are cloud service providers (CSPs); and the computer storing theother information specifying the application and the infrastructurecomponents in the CMDB, wherein the step of generating the topology isbased on the other information and infrastructure components stored inthe CMDB.
 3. The method of claim 1, further comprising the steps of: thecomputer receiving sets of APIs for respective portals of correspondingSPs which are corresponding cloud service providers (CSPs), each of thereceived sets of APIs indicating mechanisms to deploy a service on thecorresponding CSP, the mechanisms including at least one of deploying avirtual machine, configuring the virtual machine, deploying a network,configuring the network, deploying middleware, configuring themiddleware, deploying the application, and configuring the application;the computer storing the sets of APIs in the CMDB; and the computergenerating and storing rules in the CMDB, so that each rule indicatesconditions under which a corresponding set of APIs is executed to deploythe service on the corresponding CSP, wherein the step of generating thetopology includes the step of generating and storing the rules, andwherein the steps of disabling the first API and activating the secondAPI are based on the rules stored in the CMDB.
 4. The method of claim 1,further comprising the steps of: the computer receiving sets of APIs forrespective SPs which are cloud service providers (CSPs), each of thereceived sets of APIs indicating mechanisms to deploy a service on acorresponding CSP included in the CSPs; the computer generating andstoring rules in the CMDB, so that each rule indicates conditions underwhich a corresponding set of APIs is executed to deploy the service onthe corresponding CSP; the computer obtaining a subscription to aservice that sends a notification of changes to the sets of APIs; basedon the subscription, the computer receiving a notification of a changeto a set of APIs specified by a rule stored in the CMDB; and in responseto the step of receiving the notification, the computer updating therule in the CMDB based on the change to the set of APIs.
 5. The methodof claim 1, further comprising the steps of: the computer receivingfirst, second, and third information about the first service provided bythe first SP which is a first cloud service provider (CSP), the secondservice provided by the second SP which is a second CSP, and the a thirdservice provided by a third SP which is a third CSP, respectively,wherein the first, second, and third information includes geographicattributes of the first, second, and third CSPs, respectively; thecomputer determining that the second and third services provide thefunctionality of the application; the computer determining a thresholdfor a latency of the application; based on the geographic attributes inthe second information, the computer determining that redeploying theapplication to the second CSP results in a first latency of theapplication; based on the geographic attributes in the thirdinformation, the computer determining that redeploying the applicationto the third CSP results in a second latency of the application; thecomputer determining that the first latency does not exceed thethreshold and the second latency exceeds the threshold; and based on thesecond service providing the functionality of the application, the firstlatency not exceeding the threshold, and the second latency exceedingthe threshold, the computer redeploying the application to the secondCSP and not to the third CSP.
 6. The method of claim 1, wherein the stepof detecting the fail condition includes detecting an outage of anentire data center provided by the first SP which is a first cloudservice provider (CSP), the outage of the entire data center causing theoutage of the first service.
 7. The method of claim 1, furthercomprising the step of: providing at least one support service for atleast one of creating, integrating, hosting, maintaining, and deployingcomputer-readable program code in the computer, the program code beingexecuted by a processor of the computer to implement the steps ofreceiving the information specifying the services, storing the receivedinformation in the CMDB, generating the topology, detecting the failcondition, determining that the first API had provided the first serviceprior to the fail condition and that the second API provides the secondservice, disabling the first API, and activating the second API.
 8. Acomputer program product, comprising: a computer-readable storagedevice; and a computer-readable program code stored in thecomputer-readable storage device, the computer-readable program codecontaining instructions that are executed by a central processing unit(CPU) of a computer system to implement a method of managing resiliencyof an application provided by a first service provider (SP), the methodcomprising the steps of: the computer system receiving informationspecifying services which are provided by respective SPs including thefirst SP, the information indicating that each of the services providesa functionality of the application; the computer system storing thereceived information in a configuration management database (CMDB);based on the information stored in the CMDB, the computer systemgenerating a topology which maps the first SP to a second SP included inthe SPs and maps a first service provided by the first SP to a secondservice provided by the second SP, the first and second services beingincluded in the services specified by the received information;subsequent to the step of generating the topology, the computer systemdetecting a fail condition of the first SP, which indicates an outage ofthe first service provided by the first SP; in response to the step ofdetecting the fail condition and based on the topology, the computersystem determining that a first API provided by the first SP hadprovided the first service prior to the fail condition and that a secondAPI provided by the second SP provides the second service; based on thefirst API having provided the first service and the second API providingthe second service, the computer system disabling the first API providedby the first SP and activating the second API provided by the second SP,so that the functionality of the application that had been provided bythe first service prior to the fail condition being detected continuesby being provided by the second API even though the first SP isexperiencing the fail condition.
 9. The computer program product ofclaim 8, wherein the method further comprises the steps of: the computersystem receiving other information specifying the application andinfrastructure components of the SPs which are cloud service providers(CSPs); and the computer system storing the other information specifyingthe application and the infrastructure components in the CMDB, whereinthe step of generating the topology is based on the other informationand infrastructure components stored in the CMDB.
 10. The computerprogram product of claim 8, wherein the method further comprises thesteps of: the computer system receiving sets of APIs for respectiveportals of corresponding SPs which are corresponding cloud serviceproviders (CSPs), each of the received sets of APIs indicatingmechanisms to deploy a service on the corresponding CSP, the mechanismsincluding at least one of deploying a virtual machine, configuring thevirtual machine, deploying a network, configuring the network, deployingmiddleware, configuring the middleware, deploying the application, andconfiguring the application; the computer system storing the sets ofAPIs in the CMDB; and the computer system generating and storing rulesin the CMDB, so that each rule indicates conditions under which acorresponding set of APIs is executed to deploy the service on thecorresponding CSP, wherein the step of generating the topology includesthe step of generating and storing the rules, and wherein the steps ofdisabling the first API and activating the second API are based on therules stored in the CMDB.
 11. The computer program product of claim 8,wherein the method further comprises the steps of: the computer systemreceiving sets of APIs for respective SPs which are cloud serviceproviders (CSPs), each of the received sets of APIs indicatingmechanisms to deploy a service on a corresponding CSP included in theCSPs; the computer system generating and storing rules in the CMDB, sothat each rule indicates conditions under which a corresponding set ofAPIs is executed to deploy the service on the corresponding CSP; thecomputer system obtaining a subscription to a service that sends anotification of changes to the sets of APIs; based on the subscription,the computer system receiving a notification of a change to a set ofAPIs specified by a rule stored in the CMDB; and in response to the stepof receiving the notification, the computer system updating the rule inthe CMDB based on the change to the set of APIs.
 12. The computerprogram product of claim 8, wherein the method further comprises thesteps of: the computer system receiving first, second, and thirdinformation about the first service provided by the first SP which is afirst cloud service provider (CSP), the second service provided by thesecond SP which is a second CSP, and the a third service provided by athird SP which is a third CSP, respectively, wherein the first, second,and third information includes geographic attributes of the first,second, and third CSPs, respectively; the computer system determiningthat the second and third services provide the functionality of theapplication; the computer system determining a threshold for a latencyof the application; based on the geographic attributes in the secondinformation, the computer system determining that redeploying theapplication to the second CSP results in a first latency of theapplication; based on the geographic attributes in the thirdinformation, the computer system determining that redeploying theapplication to the third CSP results in a second latency of theapplication; the computer system determining that the first latency doesnot exceed the threshold and the second latency exceeds the threshold;and based on the second service providing the functionality of theapplication, the first latency not exceeding the threshold, and thesecond latency exceeding the threshold, the computer system redeployingthe application to the second CSP and not to the third CSP.
 13. Thecomputer program product of claim 8, wherein the step of detecting thefail condition includes detecting an outage of an entire data centerprovided by the first SP which is a cloud service provider, the outageof the entire data center causing the outage of the first service.
 14. Acomputer system comprising: a central processing unit (CPU); a memorycoupled to the CPU; and a computer readable storage device coupled tothe CPU, the storage device containing instructions that are executed bythe CPU via the memory to implement a method of managing resiliency ofan application provided by a first service provider (SP), the methodcomprising the steps of: the computer system receiving informationspecifying services which are provided by respective SPs including thefirst SP, the information indicating that each of the services providesa functionality of the application; the computer system storing thereceived information in a configuration management database (CMDB);based on the information stored in the CMDB, the computer systemgenerating a topology which maps the first SP to a second SP included inthe SPs and maps a first service provided by the first SP to a secondservice provided by the second SP, the first and second services beingincluded in the services specified by the received information;subsequent to the step of generating the topology, the computer systemdetecting a fail condition of the first SP, which indicates an outage ofthe first service provided by the first SP; in response to the step ofdetecting the fail condition and based on the topology, the computersystem determining that a first API provided by the first SP hadprovided the first service prior to the fail condition and that a secondAPI provided by the second SP provides the second service; based on thefirst API having provided the first service and the second API providingthe second service, the computer system disabling the first API providedby the first SP and activating the second API provided by the second SP,so that the functionality of the application that had been provided bythe first service prior to the fail condition being detected continuesby being provided by the second API even though the first SP isexperiencing the fail condition.
 15. The computer system of claim 14,wherein the method further comprises the steps of: the computer systemreceiving other information specifying the application andinfrastructure components of the SPs which are cloud service providers(CSPs); and the computer system storing the other information specifyingthe application and the infrastructure components in the CMDB, whereinthe step of generating the topology is based on the other informationand infrastructure components stored in the CMDB.
 16. The computersystem of claim 14, wherein the method further comprises the steps of:the computer system receiving sets of APIs for respective portals ofcorresponding SPs which are corresponding cloud service providers(CSPs), each of the received sets of APIs indicating mechanisms todeploy a service on the corresponding CSP, the mechanisms including atleast one of deploying a virtual machine, configuring the virtualmachine, deploying a network, configuring the network, deployingmiddleware, configuring the middleware, deploying the application, andconfiguring the application; the computer system storing the sets ofAPIs in the CMDB; and the computer system generating and storing rulesin the CMDB, so that each rule indicates conditions under which acorresponding set of APIs is executed to deploy the service on thecorresponding CSP, wherein the step of generating the topology includesthe step of generating and storing the rules, and wherein the steps ofdisabling the first API and activating the second API are based on therules stored in the CMDB.
 17. The computer system of claim 14, whereinthe method further comprises the steps of: the computer system receivingsets of APIs for respective SPs which are cloud service providers(CSPs), each of the received sets of APIs indicating mechanisms todeploy a service on a corresponding CSP included in the CSPs; thecomputer system generating and storing rules in the CMDB, so that eachrule indicates conditions under which a corresponding set of APIs isexecuted to deploy the service on the corresponding CSP; the computersystem obtaining a subscription to a service that sends a notificationof changes to the sets of APIs; based on the subscription, the computersystem receiving a notification of a change to a set of APIs specifiedby a rule stored in the CMDB; and in response to the step of receivingthe notification, the computer system updating the rule in the CMDBbased on the change to the set of APIs.
 18. The computer system of claim14, wherein the method further comprises the steps of: the computersystem receiving first, second, and third information about the firstservice provided by the first SP which is a first cloud service provider(CSP), the second service provided by the second SP which is a secondCSP, and the a third service provided by a third SP which is a thirdCSP, respectively, wherein the first, second, and third informationincludes geographic attributes of the first, second, and third CSPs,respectively; the computer system determining that the second and thirdservices provide the functionality of the application; the computersystem determining a threshold for a latency of the application; basedon the geographic attributes in the second information, the computersystem determining that redeploying the application to the second CSPresults in a first latency of the application; based on the geographicattributes in the third information, the computer system determiningthat redeploying the application to the third CSP results in a secondlatency of the application; the computer system determining that thefirst latency does not exceed the threshold and the second latencyexceeds the threshold; and based on the second service providing thefunctionality of the application, the first latency not exceeding thethreshold, and the second latency exceeding the threshold, the computersystem redeploying the application to the second CSP and not to thethird CSP.
 19. The computer system of claim 14, wherein the step ofdetecting the fail condition includes detecting an outage of an entiredata center provided by the first SP which is a first cloud serviceprovider (CSP), the outage of the entire data center causing the outageof the first service.